-
Notifications
You must be signed in to change notification settings - Fork 318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fates patch count controls #1766
Conversation
… file for testing
…h Erik we will have a different approach.
…P with MEGAN, and add tests for the FATES-SP version to aux_clm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have a bunch of comments here, and ask for a bunch of changes. Some are really reverting code in ways that won't matter for your testing. Some are bigger and we should discuss.
@rgknox and I met to go over this, and did some good work to figure this out. Steps forward that we see will be to bring in the PR I added to this PR, and Ryan is also going to work with maxveg and natpft_ub a bit. In the longer term I want to refactor the surfrd part of this, but we'll have me do that part of this. |
We built a table to show how this works for different FATES modes... https://docs.google.com/spreadsheets/d/1OJ0eaNVb1AvDOnflrsY_haMoGZR6E4NGE1fMTkxl56c |
Conflicts: src/main/clm_initializeMod.F90
…meaning with fates versus non-fates
…dd a commented out line about what the expected correct line should be
OK, I think this is nearly ready. Things left to do that I see are to merge my dry-dep changes in, and then rerun testing. After that we can merge the FATES changes in, and then do the normal things to turn this into the next CTSM tag ctsm5.1.dev099. |
Fates drydep changes
Description of changes
This PR is an API change. Primarily it allows fates to dictate the total number of naturally vegetated patches. If fates is in SP mode, it also ensures that CLM tracks enough patches to accomodate the LAI and height vectors that it needs to pass back. These modifications should move us closer (if not all the way there) to run CFTs as FATES patches as well.
Specific notes
Coupled with FATES PR: 862
Contributors other than yourself, if any:
@ekluzek fates-software-team
CTSM Issues Fixed (include github issue #):
Fixes #1764
Fixes #1762
Fixes #1784
Are answers expected to change (and if so in what way)? No bit-for-bit
Any User Interface Changes (namelist or namelist defaults changes)? New namelist item for fates
use_fates_tree_damage
Some new FATES damage dimensions
Testing performed, if any: regular and fates tests